Skip to content

Conversation

@itzmanish
Copy link

@itzmanish itzmanish commented Nov 28, 2025

This PR adds support for multi relay communication to have multiple relay's deployed and communicate about the namespaces for publishing and subscribing.

We now have a Coordinator interface which can be implemented based on user's requirement. There is already a file coordinator which uses file as a backend to store the information about the namespaces and relay url.

@itzmanish itzmanish marked this pull request as draft November 28, 2025 12:21
@itzmanish itzmanish changed the title Multi Relay with file coordinator DRAFT: Multi Relay with file coordinator Nov 28, 2025
Ok((session.into(), connection_id_hex))
}

/// Default DNS resolution logic that filters results by address family.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool - this appears to accomplish the same things I did in this PR: #111

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. Sorry I noticed this later after doing the PR. But yeah this now covers for dns resolution by considering address family. Also I am planning to pass custom dns resolution logic in a seperate PR later.

@itzmanish itzmanish marked this pull request as ready for review December 2, 2025 13:42
@itzmanish itzmanish changed the title DRAFT: Multi Relay with file coordinator Multi Relay with file coordinator Dec 2, 2025
@itzmanish itzmanish changed the title Multi Relay with file coordinator Multi Relay Communication with Coordinator Dec 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants